Latest Report | Participation Agreement | API | Validation | Encryption
[November 29, 2021] An updated FRVT MORPH report has been published, adding results for one new algorithm submitted by Hochschule Darmstadt (hdafvdet-001).
The table provides a summary of all algorithms measured on attack presentation classification error rate (APCER) when bona fide classification error rate (BPCER) is set to 0.1 and 0.01, across a subset of the different morphing datasets used in our evaluation. APCER, or morph miss rate, is the proportion of morphs that are incorrectly classified as bona fides (nonmorphs). BPCER, or false detection rate, is the proportion of bona fides falsely classified as morphs.
The table provides a summary of algorithms submitted to FRVT 1:1, measured on mated morph presentation match rate (MMPMR), where MMPMR is the proportion of morph comparisons where both subjects (incorrectly) authenticate against the morph. The threshold is set such that the false match rate (FMR) = 0.0001 on regular (nonmorphed) comparisons. The false non-match rate (FNMR) at FMR = 0.0001 on regular (nonmorphed) comparisons is listed alongside the MMPMR. The lower the MMPMR, the better the algorithm performs against morphs.
Website
Global Morph
Local Morph
Local Morph Colorized Average
Local Morph Colorized Match
UNIBO Automatic Morphed Face Generation Tool v1.0
DST
Visa-Border
UNIBO Automatic Morphed Face Generation Tool v2.0
Twente
MIPGAN-II
Manual
Lincoln
Print and Scanned
FRVT MORPH is conducted by NIST, an agency of the United States Government. Participation is free of charge. FRVT MORPH is open to a global audience of computer vision and face recognition developers. All organizations who seek to participate in FRVT MORPH must sign and submit all pages of this Participation Agreement. Note that this is a separate agreement from the FRVT Ongoing 1:1 agreement. [last update: 2018-06-11]
An updated version of the FRVT MORPH API document is now available. This update adds an optional input parameter to the function detectMorphDifferentially(). The additional parameter represents the time/age difference (in days) between a suspected morph and the live probe image. [last update: 2021-07-07]
All FRVT APIs reference the supporting FRVT General Evaluation Specifications, which includes hardware and operating system environment, software requirements, reporting, and common data structures that support the APIs. Developers must ensure that their submission conforms to the API specifications.
An updated validation package has been published. All participants must run their software through the validation package prior to submission. The purpose of validation is to ensure consistent algorithm output between your execution and NIST’s execution. [last update: 2020-09-10]
All submissions must be properly encrypted and signed before transmission to NIST. This must be done according to these instructions using the FRVT Ongoing public key linked from this page. Participants must email their public key to NIST. The participant’s public key must correspond to the participant’s public-key fingerprint provided on the signed Participation Application. [last update: 2018-05-10]
Subscribe to the FRVT mailing list to receive emails when announcements or updates are made.